perm filename UCODE.CHG[S1,ALS] blob
sn#436730 filedate 1979-04-27 generic text, type C, neo UTF8
COMMENT ā VALID 00002 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00002 00002 ABS ADD AND BGN CHK CHKF CHKH CHKL CHKN CHKT CHR CLAB COMM CSP CUP
C00005 ENDMK
Cā;
ABS ADD AND BGN CHK CHKF CHKH CHKL CHKN CHKT CHR CLAB COMM CSP CUP
DEAD Should this be used by UCPASC to free registers and memory locations?
One use would be to never reuse a memory or register as long as the
stack was not empty and then to specify the locations that can then
be cleared, when the stack is emptied.
DEC DEF DIF DIV
DMD Problem if TYPD
DOA
DUP Does this mean a) duplicate the datum on the stack or
b) duplicate the item referenced by the stack datum and put a new
datum on the stack that references this new item?
END ENT EQU FJP FLO FLT GEQ GRT
IEQU IGEQ IGRT ILEQ ILES INEQ SOPU needs fixing for these
INC IND INN INT IOR IXA LAB LCA LDA LDC LEQ LES LEX LIVE LOC LOD
MDEF MOD MOV MPY MST MUS NEG NEQ NEW NOT
NSTR What about the empty stack requirement?
ODD ORD OPTN PAR PLOD PSTR RET SGS SQR SST STO
STP STR SUB SWP SYM TJP TOF TON TRC TYP UJP UNI UNK XJP
General problems
1. The empty stack requirement.
2. DUP STR NSTR etc problem when the stack datum is an address not the item.
3. Missing parammeters in Ucode for SOPU.
4. The unused instruction problem.
5. The overflow problem with H and Q word integer arithmetic.
6. BGN label after the instruction as a parameter.
7. The D-word problem with DMD.
8. Firm list of data types (with meanings) that are to be supported.